System and Method for a Federated Evolved Packet Core Service Bus

ABSTRACT

A system and method of provides services including a federated service bus between distributed and evolved packet core (EPC) and a radio access network (RAN), wherein the federated service bus provides information based on a parent-child relationship between the EPC and RAN on a per-federated service basis. The information can include loading and location information.

This application claims the benefit of U.S. Provisional Application No. 62/025,678, entitled “System and Method for a Federated Evolved Packet Core Service Bus,” filed on Jul. 17, 2014, which application is hereby incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to a system and method for network communications, and, in particular embodiments, to a system and method for a federated evolved packet core service bus.

BACKGROUND

Applications, such as content delivery networks (CDNs) and the like can benefit from obtaining congestion information, loading of networks, user equipment (UE) location and other services. Current evolved packet core (EPC) networks can use protocol-based interfaces to provide such services to applications. For example, the Rx interface within the diameter protocolallows an application to request quality of service (QoS) to the policy and charging rules function (PCRF) of an EPC network. However, even for load information exchange among EPC functions an extension is needed to the general packet radio service (GPRS) tunneling protocol (GTP). Example EPC functions include packet data network (PDN) gateways (PGWs), serving gateways (SGWs), and mobility management entities (MMEs). Such extensions are only usable if the application complies with the aspects of the complex protocol (GTP, Diameter, etc.). However, many applications do not have facilities to handle such complex protocols and, for factors such as network loading that require constant updating, such protocols would require significant bandwidth.

SUMMARY

In an embodiment of the present invention, a method for providing services includes providing a federated service bus between distributed and evolved packet core (EPC) and a radio access network (RAN), wherein the federated service bus provides information based on a parent-child relationship between the EPC and RAN on a per-federated service basis.

In another embodiment of the present invention, a method for providing services includes providing a first service bus in communication with a plurality of radio access network functional components. A second service bus is provided that is in communication with a plurality of evolved packet core functional components. A federation bus is provided between the first service bus and second service bus. First information from the radio access network functional components is provided to the second service bus. In addition second information from the evolved packet core functional components is provided to first service bus.

Another embodiment of the present invention includes a federated service bus including at least one processor and at least one non-transitory computer readable storage medium storing programming for execution by the at least one processor. The programming includes instructions to provide a federated service bus between an evolved packet core (EPC) and a radio access network (RAN), wherein the federated service bus provides information based on a parent-child relationship between the EPC and RAN on a per-federated service basis.

Another embodiment of the present invention provides a federated service bus including a first service bus in communication with a plurality of radio access network functional components. A second service bus is provided in communication with a plurality of evolved packet core functional components. A federation bus between the first service bus and second service bus is provided, wherein first information from the radio access network functional components is provided to the second service bus and second information from the evolved packet core functional components is provided to first service bus.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIG. 1 shows a wireless access configuration on the LTE model;

FIG. 2 shows an embodiment of the present invention that provides a subscriber bus in an EPC 220;

FIG. 3 shows an embodiment of the present invention that provides a subscriber bus in an RAN 220;

FIG. 4 shows an embodiment of the present invention including a federated service bus;

FIG. 5 is a process flow diagram showing a method embodiment that provides user equipment (UE) location service that allows an application to obtain the 3GPP location information of a UE, given the IP address of the flow;

FIG. 6 is an illustration of another embodiment of the present invention in a more complex network including multiple EPCs;

FIG. 7 illustrates a method embodiment of the present invention using cell congestion/load information in an embodiment such as network 600;

FIG. 8 shows another embodiment of the present invention related routing WiFi connections to 3GPP EPC (using S2a protocol);

FIG. 9 illustrates a process of S2a-EPC (PGW) selection in the embodiment of FIG. 8;

FIG. 10 illustrates another process of S2a-EPC (PGW) selection in the embodiment of FIG. 8;

FIG. 11 shows an embodiment of the present invention to illustrate LTE-EPC selection;

FIG. 12 shows a process for providing EPC loading information;

FIG. 13 illustrates a block diagram of an embodiment processing system 1300 for performing methods described herein, which may be installed in a host device; and

FIG. 14 illustrates a block diagram of a transceiver 1400 adapted to transmit and receive signaling over a telecommunications network.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The structure, manufacture and use of the presently preferred embodiments are discussed in detail below. It should be appreciated, however, that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.

FIG. 1 shows a simplified wireless access configuration on the LTE model. Access network 100 includes radio transceivers 102 a and 102 b, which are configured to communicate with UE 104. Radio transceivers 102 a and 102 b communicate to radio access network (RAN) 106 in two ways. First, a direct connection is provided to OpenFlow (OF) controller 108. OF controller 108 controls RAN OF backhaul platform 110, which serves as a platform for the RAN backhaul 112 operating as software defined elements. Transceiver 102 a, transceiver 102 b and RAN 106 is, for example, are part of an E-UTRAN configuration as defined by 3GPP TS 36.300, entitled Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), which is hereby incorporated by reference into this specification in its entirety).

RAN 106 is connected to evolved packet core (EPC) 120 using S1 protocols 116 as defined by the 3GPP. As with RAN 106, EPC 120 is configured in a software defined configuration with OF controller 122 controlling EPC OF platform 124, which supports EPC functions 126. In this example, the EPC functions include the functions defined for an EPC by the 3GPP TS 23.402 which is hereby incorporated by reference into this specification in its entirety). Specific functions may include, but are not limited to, the mobility management entity (MME), packet data network (PDN) gateway (PGW) and home subscriber server (HSS).

In addition to the core LTE functionality of RAN 106 and EPC 120 described above, both RAN 106 and EPC 124 may include applications for additional functionality in the control plane. App 130 maybe a load balancer or another function. In FIG. 1, EPC 120 includes two content data network (CDN) optimizers 132 and 134. The CDNs optimize the use of cloud processing and storage for the delivery of content to UEs. These functions (App 130 and CDNs 132 and 134) communicate with the RAN functions 112 and the EPC functions 126. In addition, using the control plane, these functions communicate with radio transceivers 102 a and 102 b, and with external networks using a network consisting of local Ethernet network 140, gateways 142, 144 and 146, aggregation network 148, and gateway 150. However, using prior techniques, there is no efficient way for applications in the EPC 120 to access data involving the RAN functions 112 or for applications running in the RAN 106 to access data involving the EPC functions 126.

FIG. 2 shows an embodiment of the present invention that provides a subscriber bus in an EPC 220. The EPC service bus (EPC-SB) is a loosely coupled, service oriented architecture to exchange information (publish/subscribe/notify and request/response) between EPC/RAN and an application. Examples of services include: UE location information, network load information, and cell congestion. The federation of the service bus is supported with a parent-child relationship per service. That is, producers of info register with the parent. Then, consumers of the information subscribe to the parent, or if federated they subscribe to the child (which acts as a broker to obtain the info from the parent). As examples, the EPC-SB would be the parent for UE location service, while, for cell congestion service, the RAN service bus (RAN-SB) would be the parent.

As with EPC 120 (FIG. 1), EPC 220 includes EPC functions 126 and CDN optimizers 132 and 134. However, EPC 220 includes EPC service bus (EPC-SB) 222. EPC-SB 222 provides a mechanism to expose capabilities on a per service basis (that is, the application does not need to implement any other details), as well as a messaging system by which these capabilities/services can be provided. EPC-SB 222 includes a service router 224 and a service registry 226. In addition, EPC-SB includes a service policy store 228 and a service model store 230. EPC-SB operates on a subscription basis. That is, an application subscribes to the load information for a cell that is regularly gathered and stored from the EPC functions 126 and the subscribing entity is notified on regular basis of this information.

FIG. 3 shows an embodiment of the present invention that provides a subscriber bus in an RAN 220. Similarly to EPC 220, RAN 206 includes RAN functions 112 and application 130 as in RAN 106 (FIG. 1). In addition, RAN 206 includes RAN service bus (RAN-SB) 208. As with EPC-SB 222, RAN-SB 208 includes a service router 210 and a service registry 212. In addition, RAN-SB includes a service policy store 214 and a service model store 216. As with EPC-SB 222, RAN-SB 208 operates on a subscription basis.

FIG. 4 shows an embodiment of the present invention including a federated service bus. In network 400, items bearing numbers from FIG. 1-3 provide the functions described in those figures. In addition, RAN-SB 208 and EPC-SB 222 are connected by federation bus 410. Together, RAN-SB 208, EPC-SB 222 and federation bus 410 combine to function as a federated bus. This allows functions in RAN 206 to subscribe to information in that EPC 220 allows to be exposed and vice-versa. The federation of EPC-SB 222 and RAN-SB 208 exposes various services to applications, such as intelligent domain name server (iDNS), content network proxy, etc. This allows those applications to provide different services, including radio/cell location information for an internet protocol (IP) flow or connection, an out-of-band service mechanism to return radio network location information for an IP flow/connection, and radio/cell load information. This provides a federation of services between distributed EPC and RAN sites with a parent-child relationship on a per-federated service basis.

Applications such as iDNS, content delivery, and other emerging applications can benefit from understanding the radio network location for an IP flow and congestion level in radio networks. It is also understood that placing proxies close to the RAN network can improve the CDN service delivered. Such proxies use heuristics based on round trip time (RTT), IP address locality, and other aggregate information to derive a personalized and optimal content delivery service. An application such as CDN proxy can use cell load and explicit congestion information (ECN) (congestion experience (CE) information) on a traffic path to determine the best way to deliver content to a user.

However, using prior techniques, there are no well-defined mechanisms to provide cell congestion feedback to such applications. Prior techniques require modification or encapsulation in each traffic packet. The embodiment of FIG. 4 provides an out-of-band mechanism to return, for example, radio network location information for an IP flow/connection or cell load information. To access this information, an application subscribes to the information for a cell and is notified on regular basis.

FIG. 5 is a process flow diagram showing a method embodiment that provides user equipment (UE) location service that allows an application to obtain the 3GPP location information of a UE, given the IP address of the flow. In step 501, the EPC-SB 222 registers as the parent (<UE-Location-Service>) and makes the service available to the RAN 206 and EPC 220. In step 504, one of several types of messages from UE 104 (Attach, TAU/RAU Request, Path Switch Request, Handover Notify) trigger EPC 220 (MME) to publish the location of UE 104 (<UE-Location-Service> (op=INSERT, key=UE IMSI, MSISDN, location=cell id, TA/RA id, {list IP/PDN address}). Because EPC-SB 222 is registered as a parent for this information, the location information is stored in EPC-SB 222 in step 506. In step 508, if an EPC function 126 subscribes to the location information, the EPC-SB will return the information in step 510. More importantly, components outside of the EPC functions 126 can subscribe using federated bus 410. In step 512, an application such as application 130 subscribes to the location information that the EPC-SB 222 federates and exposes to application 130 through RAN-SB 208. Other applications (e.g. iDNS, CDN optimizer) that request for location information with similar semantics (<UE-Location-Service> (op=REQUEST, IP-prefix=IPx). EPC-SB returns <UE-Location-Service> (op=RESPONSE, IP-prefix=IPx, TA=tal, cell-id=c1, . . . ). Publish/Subscribe/Notify based <UE-Location-Service>) may also be enabled. Applications may use the TA, cell-id and other configured topology and load info to select appropriate gateways, servers, etc. Of importance, transferring this information does not require the use of complex protocol extensions or burden the primary data plane or control plane functions of network 400.

FIG. 6 is an illustration of another embodiment of the present invention in a more complex network including multiple EPCs. In a distributed architecture where there are multiple EPC sites that RAN networks can home to, a mechanism is needed by which a RAN network can select one out of many EPC sites for each new session that is being established. Using prior technology, there may be multiple MMEs (potentially distributed) that can direct the attach/session setup request. The distribution among multiple MMEs is usually based on weighted configuration in a DNS on a tracking area code (TAC). However, these mechanisms are relatively static and do not account for dynamic load on each MME/associated EPC servers. In a largely centralized EPC (as in current deployments), this method can work well. However, in highly distributed EPC networks, more dynamic methods are needed. In addition to effective load balancing, geographical redundancy can benefit from such methods. The embodiment of FIG. 6 how the present invention provides these benefits.

Network 600 includes five transceivers 102 a-e. Any of these transceivers may utilize one of three RANs 206 a-c. Each of RANs 206 a-c includes RAN functions 112 a-c, respectively, RAN-SBs 208 a-c, respectively, OF controllers 108 a-c, respectively, and Ethernet ports 602 a-c, respectively. All of transceivers 102 a-e and Ethernet ports 602 a-c connect to local Ethernet 140. In addition, two EPCs 220 a-b are provided. Both of EPCs 220 a-b include EPC functions 126 a-b, respectively, EPC-SBs 222 a-b, respectively, OF controllers 122 a-b, respectively, gateways 142 a-b and 144 a-b, respectively and CDN optimizers 132 a-b, respectively. Gateways 142 a-b connect to the aggregation network 148 via gateway 146 a and gateways 144 a-b connect to aggregation network 148 via gateway 146 b. In addition, each of EPCs 220 a-b includes an intelligent internal domain name servers (iDNSs) 604 a-b. A typical DNS includes a relatively fixed mapping for routing packets. iDNS servers are valuable in this embodiment because they can be updated dynamically. This allows them to select a routing that avoids problems, if information regarding the problems is provided to them. In addition, each of RAN-SBs 208 a-c includes federation buses 410 a-c, respectively. Each of federation buses 410 a-c includes two buses, one connects to EPC-SB 222 a and the other to EPC-SB 222 b. Therefore, all of RAN-SBs 208 a-c and federated with both of EPC-SBs 222 a-b. FIG. 6 illustrates service bus logical connections. However, federation buses 4101-c may take other configurations such as a central broker system or point-to-point distribution.

FIG. 7 illustrates a method embodiment of the present invention using cell congestion/load information in an embodiment like network 600. In step 702, one of RAN-SBs 208 a-c is the parent of this service and EPC functions may subscribe to it via EPC-SB 222 (CDN-Opt 132 a-b is an example application). In step 704, the Uu interface in transceivers 102 a-e provides channel congestion, interference and other data that RAN functions 112 a-c aggregate as load information (percentage, channels, other info). In step 706, the RAN functions 112 a-c publish the information to RAN-SBs 208 a-c. Because the service is federated, the subscribers in other domains are informed (e.g., <Cell-congestion> (op=PUBLISH, cell id=x, congestion level=y). In step 708, applications like CDN-opt 132 a-b subscribe to the load information. In step 710, the RAN-SBs 208 a-c forward this information and it is consumed by CDN-opt 132 a-b to optimize providing cloud based information. Specifically, CDN-opt uses <Cell-Congestion> for overall and coarse grained information to optimize CDN services. It also uses ECN marking on upstream flows for fine-grained optimization of CDN services for specific flows.

FIG. 8 shows another embodiment of the present invention related to routing WiFi connections to 3GPP EPC (using S2a protocol). Current architectures using trusted wireless local area network (WLAN) access gateway (TWAG) do not consider dynamic load balancing among multiple packet data network gateways (PGWs) or other sites. With the embodiment of FIG. 8, the EPC 220 a-b (AAA Proxy, PGW) dynamically uses a service bus 222 a-b, respectively, through resource monitors 810 a-b, respectively to distribute load information to applications that subscribe to it. In this configuration RANs 206 a-b include TWANs 806 a-b, respectively, along with TWAG 808 a-b, respectively. In this case iDNSs 804 a-b subscribe to EPC site load information. The iDNSs 804 a-b then use configuration, topology and load information to return service records (SRV) and name authority pointer (NAPTR) responses.

FIG. 9 illustrates a process of S2a—EPC (PGW) selection in the embodiment of FIG. 8. In step 902, EPC functions 126 a-b through resource monitors 810 a-b continuously register load and related information of individual components. For this service, the EPCs 220 a-b are the parents and the federated service bus provides the information to RAN applications that have registered. Resource monitors 810 a-b calculate aggregate load level of their respective EPCs at regular intervals (in terms of percentage load, session handling capacity remaining, etc.) and load the service to the service bus (<EPC-Site-Load> (op=REGISTER, site=uEPC-x)). In step 904, iDNSs 804 a-b subscribe to EPC site load, for each EPC site that cloud RANs 206 a-b are respectively configured to interact with. Since this is a federated service, RAN-SB supports the subscription (<EPC-Site-Load> (op=SUBSCRIBE, site=uEPC-x)).

FIG. 10 illustrates another process of S2a—EPC (PGW) selection in the embodiment of FIG. 8. In step 1002, resource monitors 810 a-b aggregate load level information and publishes it at regular intervals (<EPC-Site-Load> (op=PUBLISH, site=uEPC-x, load=r). In step 1004, other applications (iDNS 804 a-b in this example) subscribe to this information. In step 1006, EPC-SBs 222 a-b distribute the load information to all applications that have subscribed to the load information. In step 1008, following authentication, UE 104 sends a L3 Attach to one of TWAGs 808 a-b to set up a connection. For purposes of describing the next steps, it is assumed that TWAG 808 a is attached to UE 104. In step 1010, TWAG 808 a sends a request to iDNSs 804 a for SRV/NAPTR translation for EPCs 220 a-b. Since the RANs 206 a-b are homed to multiple EPC locations, the same UE identity may be served by multiple EPC locations. iDNSs 804 a provides an ordered list for TWAG 808 a. In step 1014, assuming that gateway 142 a is the gateway selected from the list provided by iDNS 804 a, TWAG 808 a sends Create Session request to gateway 142 a.

FIG. 11 shows an embodiment of the present invention to illustrate LTE-EPC selection. FIG. 11 shows transceivers 102 a-c connected through Ethernet network 140 for data transport. UE 104 connects through one of the transceivers and RANs 206 a-b determine the routing of the data traffic using the following processes.

FIG. 12 shows a process for providing EPC loading information. In step 1202, EPC functions 126 a-b continuously register load and related information of individual components to resource monitors 810 a-b. For this service, the EPC is the parent and the federated service bus provides the information to RAN applications that have registered. Resource monitors 810 a-b calculate aggregate load level of EPC at regular intervals (in terms of percentage load, session handling capacity remaining, etc.). Resource monitors 810 a-b registers load service to the service bus (<EPC-Site-Load> (op=REGISTER, site=uEPC-x)). In step 1204, iDNSs 804 a and/or 804 b subscribes to EPC site load, for each EPC site that RANs 206 a-b are configured to interact with. Since this is a federated service, RAN-SBs 208 a-b support the subscription and in step 1206, the EPC-SBs deliver the load information (<EPC-Site-Load> (op=SUBSCRIBE, site=uEPC-x)). In step 1208, following authentication, UE 104 sends an Attach Request to at least one of RAN functions 112 a-b to set up a session. In step 1210, the RAN functions 112 a-b requests from the iDNS 804 a-b the SRV/NAPTR translation for selecting an EPC. Since the RANs 206 a-b are homed to multiple EPC locations, the same UE identity may be served by multiple EPC locations. RAN iDNS 804 a-b provides an ordered list in step 1212. In step 1214, the RAN function responsible for the Attach Request sends the request to the EPC function 126 a-b (MME) in the selected EPC 220 a-b.

FIG. 13 illustrates a block diagram of an embodiment processing system 1300 for performing methods described herein, which may be installed in a host device. For example, RAN 206 of FIG. 3 may be implemented the processing system 1300, as well as many other described components. As shown, the processing system 1300 includes a processor 1304, a memory 1306, and interfaces 1310-1314, which may (or may not) be arranged as shown in FIG. 13. The processor 1304 may be any component or collection of components adapted to perform computations and/or other processing related tasks, and the memory 1306 may be any component or collection of components adapted to store programming and/or instructions for execution by the processor 1304. In an embodiment, the memory 1306 includes a non-transitory computer readable medium. The interfaces 1310, 1312, 1314 may be any component or collection of components that allow the processing system 1300 to communicate with other devices/components and/or a user. For example, one or more of the interfaces 1310, 1312, 1314 may be adapted to communicate data, control, or management messages from the processor 1304 to applications installed on the host device and/or a remote device. As another example, one or more of the interfaces 1310, 1312, 1314 may be adapted to allow a user or user device (e.g., personal computer (PC), etc.) to interact/communicate with the processing system 1300. The processing system 1300 may include additional components not depicted in FIG. 13, such as long term storage (e.g., non-volatile memory, etc.).

In some embodiments, the processing system 1300 is included in a network device that is accessing, or part otherwise of, a telecommunications network. In one example, the processing system 1300 is in a network-side device in a wireless or wireline telecommunications network, such as a base station, a relay station, a scheduler, a controller, a gateway, a router, an applications server, or any other device in the telecommunications network. In other embodiments, the processing system 1300 is in a user-side device accessing a wireless or wireline telecommunications network, such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communications device (e.g., a smartwatch, etc.), or any other device adapted to access a telecommunications network.

In some embodiments, one or more of the interfaces 1310, 1312, 1314 connects the processing system 1300 to a transceiver adapted to transmit and receive signaling over the telecommunications network. FIG. 14 illustrates a block diagram of a transceiver 1400 adapted to transmit and receive signaling over a telecommunications network. The transceiver 1400 may be installed in a host device. Transceiver may be use to implement, for example, one or more of transceivers 102 a-e of FIG. 6. As shown, the transceiver 1400 comprises a network-side interface 1402, a coupler 1404, a transmitter 1406, a receiver 1408, a signal processor 1410, and a device-side interface 1412. The network-side interface 1402 may include any component or collection of components adapted to transmit or receive signaling over a wireless or wireline telecommunications network. The coupler 1404 may include any component or collection of components adapted to facilitate bi-directional communication over the network-side interface 1402. The transmitter 1406 may include any component or collection of components (e.g., up-converter, power amplifier, etc.) adapted to convert a baseband signal into a modulated carrier signal suitable for transmission over the network-side interface 1402. The receiver 1408 may include any component or collection of components (e.g., down-converter, low noise amplifier, etc.) adapted to convert a carrier signal received over the network-side interface 1402 into a baseband signal. The signal processor 1410 may include any component or collection of components adapted to convert a baseband signal into a data signal suitable for communication over the device-side interface(s) 1412, or vice-versa. The device-side interface(s) 1412 may include any component or collection of components adapted to communicate data-signals between the signal processor 1410 and components within the host device (e.g., the processing system 600, local area network (LAN) ports, etc.).

The transceiver 1400 may transmit and receive signaling over any type of communications medium. In some embodiments, the transceiver 1400 transmits and receives signaling over a wireless medium. For example, the transceiver 1400 may be a wireless transceiver adapted to communicate in accordance with a wireless telecommunications protocol, such as a cellular protocol (e.g., long-term evolution (LTE), etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, near field communication (NFC), etc.). In such embodiments, the network-side interface 1402 comprises one or more antenna/radiating elements. For example, the network-side interface 1402 may include a single antenna, multiple separate antennas, or a multi-antenna array configured for multi-layer communication, e.g., single input multiple output (SIMO), multiple input single output (MISO), multiple input multiple output (MIMO), etc. In other embodiments, the transceiver 1400 transmits and receives signaling over a wireline medium, e.g., twisted-pair cable, coaxial cable, optical fiber, etc. Specific processing systems and/or transceivers may utilize all of the components shown, or only a subset of the components, and levels of integration may vary from device to device.

Further disclosed is a federated service bus means that comprises at least one processor; and at least one non-transitory computer readable storage medium storing programming for execution by the at least one processor, the programming including instructions to provide a federated service bus between an evolved packet core (EPC) and a radio access network (RAN), wherein the federated service bus provides information based on a parent-child relationship between the EPC and RAN on a per-federated service basis.

While this invention has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to persons skilled in the art upon reference to the description. It is therefore intended that the appended claims encompass any such modifications or embodiments. 

What is claimed is:
 1. A method of providing services comprising: providing a federated service bus between distributed and evolved packet core (EPC) and a radio access network (RAN), wherein the federated service bus provides information based on a parent-child relationship between the EPC and RAN on a per-federated service basis.
 2. The method of claim 1, wherein at least one federated service comprises providing location information of a user equipment (UE).
 3. The method of claim 1, wherein at least one federated service comprises a cell congestion service that allows an application to obtain a congestion level of a cell.
 4. The method of claim 1, further comprising selecting a packet data network (PDN) gateway (GW) in 3GPP S2a when there are equivalent PDN GWs in multiple sites based on load information provided via the federated service bus.
 5. The method of claim 1, further comprising selecting one of a plurality of EPCs based on load information provided via the federated service bus.
 6. A method of providing services comprising: providing a first service bus in communication with a plurality of radio access network functional components; providing a second service bus in communication with a plurality of evolved packet core functional components; and providing a federation bus between the first service bus and second service bus, wherein first information from the radio access network functional components is provided to the second service bus and second information from the evolved packet core functional components is provided to first service bus.
 7. The method of claim 6 wherein the first and second information is provided on a parent-child basis.
 8. The method of claim 6 wherein the first information is cell congestion information.
 9. The method of claim 6 wherein the second information is user equipment (UE) location information.
 10. The method of claim 6 wherein the first and second information is utilized by a content data network optimizer.
 11. A federated service bus comprising: at least one processor; and at least one non-transitory computer readable storage medium storing programming for execution by the at least one processor, the programming including instructions to: provide a federated service bus between an evolved packet core (EPC) and a radio access network (RAN), wherein the federated service bus provides information based on a parent-child relationship between the EPC and RAN on a per-federated service basis.
 12. The federated service bus of claim 11, wherein at least one federated service comprises providing location information of a user equipment (UE).
 13. The federated service bus of claim 11, wherein at least one federated service comprises a cell congestion service that allows an application to obtain a congestion level of a cell.
 14. A federated service bus comprising: a first service bus in communication with a plurality of radio access network functional components; a second service bus in communication with a plurality of evolved packet core functional components; and a federation bus between the first service bus and second service bus, wherein first information from the radio access network functional components is provided to the second service bus and second information from the evolved packet core functional components is provided to first service bus.
 15. The federated service bus of claim 14, wherein the first and second information includes location information of a user equipment (UE).
 16. The federated service bus of claim 14, wherein the first and second information includes a congestion level of a cell.
 17. The federated service bus of claim 14, further comprising: a plurality of packet data network (PDN) gateways (PGWs), wherein the first or second service bus provides information for selecting one of the PGWs based on load information provided via the federated service bus.
 18. The federated service bus of claim 14, further comprising: a plurality of evolved packet cores (EPCs), wherein the first or second service bus provides information for selecting one of the plurality of EPCs based on loading of each of the pluralities of EPCs.
 19. The federated service bus of claim 14 further comprising a content data network optimizer, wherein the first and second information is utilized by the content data network optimizer. 